Summary

Fixes #230 by teaching the VS Code-compatible providers to look in VSCodium storage roots, not only Microsoft VS Code roots.

The bug was straightforward: VSCodium uses the same extension storage layout as VS Code, but stores it under VSCodium/User/.... Before this PR, CodeBurn could parse these providers correctly once pointed at the right files, but discovery never reached those files for VSCodium users.

What changed

• Copilot discovery now checks VS Code, VS Code Insiders, and VSCodium workspaceStorage roots.
• Cline-family discovery now accepts multiple globalStorage roots instead of a single directory.
• Roo Code and Kilo Code now scan VS Code, VS Code Insiders, and VSCodium globalStorage roots.
• Missing editor roots are skipped quietly, so users with only one editor installed keep the same behavior.
• Path helpers accept injected homeDir / platform values so macOS, Linux, and Windows paths can be tested deterministically.

Example

A VSCodium user can have valid usage files under paths like:

~/Library/Application Support/VSCodium/User/workspaceStorage/...
~/.config/VSCodium/User/globalStorage/...
%APPDATA%/VSCodium/User/globalStorage/...

Those sessions now flow through the same Copilot/Roo/Kilo parsers as the existing VS Code paths instead of being invisible to CodeBurn.

Validation

• npx vitest run tests/providers/vscode-cline-parser.test.ts tests/providers/copilot.test.ts tests/providers/roo-code.test.ts tests/providers/kilo-code.test.ts — 42/42 passed.
• npx tsc --noEmit --pretty false — passed.
• npm run build — passed.
• git diff --check — passed.
• Argus-style local review — PASS.
• Claude Opus 4.7 effort max review — PASS.
• Gemini 3.1 Pro Preview review — PASS.
• GitHub checks check, semgrep, and assess — passed.

Notes

I did not include real local VSCodium usage data here. Validation uses synthetic path fixtures and parser tests, so no local project names, prompts, paths, session IDs, usage values, or private product details are exposed.